chore(#4165): rename llamastack to ogx across boost workspace - #4167

Changed Packages

Codecov Report

❌ Patch coverage is 66.66667% with 11 lines in your changes missing coverage. Please review.
✅ Project coverage is 54.96%. Comparing base (234bc78) to head (0bd187d).
✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##             main    #4167   +/-   ##
=======================================
  Coverage   54.96%   54.96%           
=======================================
  Files        2413     2413           
  Lines       96074    96074           
  Branches    26898    26898           
=======================================
  Hits        52809    52809           
  Misses      41770    41770           
  Partials     1495     1495           

/fs-fix add changesets via the process articulated in https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md#creating-changesets for all affected packages and plugins; add a yarn directive into package.json if needed that replicates what is done in other workspaces

🤖 Finished Fix · ✅ Success · Started 4:09 PM UTC · Completed 4:16 PM UTC
Commit: 928a64d · View workflow run →

🔧 Fix agent — iteration 1 (human-triggered)

Added changeset for the llamastack-to-ogx rename covering all 4 affected public packages (2 minor for renamed packages, 2 patch for internal reference updates). No yarn directive needed — boost already has @changesets/cli configured identically to other workspaces.

Fixed (1):

1. add changesets for all affected packages and plugins: Created changeset file at workspaces/boost/.changeset/rename-llamastack-to-ogx.md covering all 4 affected non-private packages: boost-backend-module-ogx (minor - package renamed), ogx-entity-provider (minor - package renamed), boost-backend (patch - internal string changes), and boost-common (patch - JSDoc/test comment changes). The backend package is private and does not need a changeset.

Disagreed (1):

1. add a yarn directive into package.json if needed: No additional yarn directive is needed. The boost workspace already has @changesets/cli (^2.27.1) in devDependencies and a .changeset/config.json. No other workspace in the repo has a dedicated changeset script in package.json — they all rely on @changesets/cli providing the changeset binary, making yarn changeset work out of the box. The boost workspace already follows this same pattern.

Tests: passed

_{Updated by fullsend fix agent}

/fs-review

🤖 Finished Review · ✅ Success · Started 4:24 PM UTC · Completed 4:42 PM UTC
Commit: 66f2e8d · View workflow run →

Review

Findings

High

• [stale-reference] workspaces/boost/scripts/load-secrets.sh:61 — The load-secrets.sh script discovers and exports BOOST_LLAMA_STACK_URL, but app-config.yaml was changed to read BOOST_OGX_URL. After merge, developers sourcing this script will have the URL exported under the wrong env var name, and the config will silently fall back to http://localhost:8321. The function name _discover_llama_stack_route and warning messages also reference the old name.
  Remediation: Rename BOOST_LLAMA_STACK_URL → BOOST_OGX_URL and _discover_llama_stack_route → _discover_ogx_route throughout scripts/load-secrets.sh.

Medium

• [npm-package-rename] workspaces/boost/.changeset/rename-llamastack-to-ogx.md — Two previously published npm packages (@red-hat-developer-hub/backstage-plugin-boost-backend-module-llamastack v0.1.2, @red-hat-developer-hub/backstage-plugin-llamastack-entity-provider v0.1.1) are renamed without deprecation of the old package names. Downstream consumers depending on the old names will see resolution failures. The changeset documents the rename, and v0.x packages allow breaking changes under semver conventions, but npm deprecate on the old names after publishing would ease the transition.

Low

• [grammar-error] workspaces/boost/dynamic-plugins-filesystem-reference.yaml:39 — Comment reads "connects to a OGX Responses API endpoint" — should be "an OGX" (vowel sound).
• [grammar-error] workspaces/boost/dynamic-plugins-image-reference.yaml:38 — Same grammar issue: "a OGX" → "an OGX".
• [stale-reference] workspaces/boost/staged-issues.md — 9 references to old naming (llamastack, Llama Stack, boost-backend-module-llamastack) remain across lines 272, 287, 292, 346, 355, 448. This planning document is not explicitly exempted as a historical record in the PR description (unlike CHANGELOG.md and openspec/specification docs).
• [config-path-breaking-change] workspaces/boost/plugins/boost-backend-module-ogx/src/provider/ResponsesApiProviderFactory.ts — Config paths boost.providers.llamastack → boost.providers.ogx and boost.entityProviders.llamastack → boost.entityProviders.ogx changed without a migration shim. Expected for v0.x rename; document in release notes.
• [catalog-entity-identity-change] workspaces/boost/plugins/ogx-entity-provider/src/providers/OgxModelEntityProvider.ts — Entity name prefixes change from llamastack-* to ogx-*; old entities become catalog orphans. Expected for v0.x rename; document in release notes.
• [cache-key-migration] workspaces/boost/plugins/boost-backend-module-ogx/src/provider/SessionMap.ts — Cache key prefixes change from llamastack: to ogx:. Existing cached data (sessions, client state, MCP auth tokens) becomes inaccessible. Impact is transient — all caches have TTLs ≤ 24h.
• [dynamic-plugin-path-change] workspaces/boost/dynamic-plugins-filesystem-reference.yaml:39 — Dynamic plugin reference paths changed. Deployed RHDH instances must update their dynamic-plugins.yaml.

Labels: All changes are within the boost workspace (workspaces/boost/)

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

/fs-fix Rename BOOST_LLAMA_STACK_URL to BOOST_OGX_URL and _discover_llama_stack_route to _discover_ogx_route throughout scripts/load-secrets.sh

🤖 Finished Fix · ✅ Success · Started 5:15 PM UTC · Completed 5:21 PM UTC
Commit: 66f2e8d · View workflow run →

From review #4167 (comment) only addressing

High
[stale-reference] workspaces/boost/scripts/load-secrets.sh:61 — The load-secrets.sh script discovers and exports BOOST_LLAMA_STACK_URL, but app-config.yaml was changed to read BOOST_OGX_URL. After merge, developers sourcing this script will have the URL exported under the wrong env var name, and the config will silently fall back to http://localhost:8321. The function name _discover_llama_stack_route and warning messages also reference the old name.
Remediation: Rename BOOST_LLAMA_STACK_URL → BOOST_OGX_URL and _discover_llama_stack_route → _discover_ogx_route throughout scripts/load-secrets.sh.

wrt to the npm deprecate all npm manipulation is done from CI ... we don't have authority to do that from the command line like the review comment suggests

not wasting tokens on any of the low's ... in particular I want staged-issues.md to only reflect the state of things when those github issues were processed ; don't need to updates as the workspace progresses

🔧 Fix agent — iteration 2 (human-triggered)

Renamed BOOST_LLAMA_STACK_URL to BOOST_OGX_URL and _discover_llama_stack_route to _discover_ogx_route throughout scripts/load-secrets.sh per human instruction, completing the llamastack-to-ogx rename in this file.

Fixed (2):

1. Rename BOOST_LLAMA_STACK_URL to BOOST_OGX_URL in load-secrets.sh (workspaces/boost/scripts/load-secrets.sh): Renamed all occurrences of BOOST_LLAMA_STACK_URL to BOOST_OGX_URL (variable assignment, export, conditional check, and echo output)
2. Rename _discover_llama_stack_route to _discover_ogx_route in load-secrets.sh (workspaces/boost/scripts/load-secrets.sh): Renamed function _discover_llama_stack_route to _discover_ogx_route (function definition, invocation, and unset -f call), and updated related comments and warning messages to reference OGX instead of Llama Stack

Tests: passed

_{Updated by fullsend fix agent}

Quality Gate failed

Failed conditions
6.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

I checked out this PR's branch and the llamastack entity provider works as expected

evidence of the rename in the backend logs:

2026-08-04T18:20:33.133Z catalog info Refreshing model entities from OGX at https://llamastack-llamastack.apps.gmontero420.rhdh-pai.devfile-ci.com target="ogx-model-entity-provider"
2026-08-04T18:20:33.349Z catalog info Fetched 367 model entities from OGX target="ogx-model-entity-provider"
2026-08-04T18:21:33.359Z catalog info Refreshing model entities from OGX at https://llamastack-llamastack.apps.gmontero420.rhdh-pai.devfile-ci.com target="ogx-model-entity-provider"
2026-08-04T18:21:33.581Z catalog info Fetched 367 model entities from OGX target="ogx-model-entity-provider"

🤖 Finished Retro · ✅ Success · Started 6:24 PM UTC · Completed 6:44 PM UTC
Commit: 0bd187d · View workflow run →

Retro: PR #4167 — rename llamastack → ogx across boost workspace

Timeline

1. 14:57 UTC — gabemontero opens issue #4165 requesting rename. Scope lists "typescript files, markdowns, or app-config.yaml examples."
2. 14:58–15:03 UTC — Triage agent runs successfully (run 30921748967), identifies affected packages and recommends approach.
3. 15:38–16:03 UTC — Code agent runs (run 30925207455), produces commit 928a64d renaming 46 files. Misses scripts/load-secrets.sh and changeset file.
4. ~16:08 UTC — Human triggers /fs-fix to add changesets. Fix agent adds changeset (commit 66f2e8d).
5. ~16:23 UTC — Human triggers /fs-review. Review agent submits CHANGES_REQUESTED at 16:42 UTC with a HIGH finding: load-secrets.sh still exports BOOST_LLAMA_STACK_URL but app-config.yaml now reads BOOST_OGX_URL.
6. 16:42 UTC — Auto-dispatch of fix agent after review fails (bot name mismatch in routing + LoadWithBase harness error).
7. ~17:14 UTC — Human manually triggers /fs-fix with specific instructions for load-secrets.sh. Fix agent completes (commit 0bd187d).
8. 18:22 UTC — gabemontero approves after manual verification against a live OGX endpoint. PR merged at 18:23 UTC.

What went well

• Review agent caught a real bug. The HIGH finding about load-secrets.sh env var mismatch was 100% accurate and would have caused a silent runtime fallback to http://localhost:8321. Both HIGH findings were fixed before merge.
• Triage quality was good. The triage agent correctly identified all affected packages and recommended a sound approach.
• Code agent handled a large rename competently. 46 files across TypeScript, config, docs, and tests were correctly renamed in a single commit — the bulk of the work was correct.

What could go better

• Two fix iterations were needed — one for changesets, one for load-secrets.sh. Both are addressable with better repo-level context.
• Auto-dispatch was broken. All 4 pull_request_target fullsend.yaml runs failed to route because bot accounts lack collaborator permissions. The pull_request_review run also failed to auto-dispatch fix because the routing logic constructs redhat-developer-review[bot] but the actual reviewer is fullsend-ai-review[bot]. Human had to manually trigger both /fs-review and /fs-fix.
• Review agent got 422 errors when posting inline comments on the diff, so all findings were included in the review body instead.

Existing issues this retro found evidence for

• rhdh-plugins#3745 (changeset instructions in agent config): This PR is another instance where the code agent omitted changesets, requiring a /fs-fix iteration. Same pattern as the original issue.
• rhdh-plugins#4166 (restore review dispatch for bot-authored PRs): This PR confirms the dispatch failure pattern — all pull_request_target runs failed to route because fullsend-ai-coder[bot] has no collaborator permission.
• fullsend#5446 (LoadWithBase harness errors): The .fullsend/rhdh/harness/code.yaml and fix.yaml both failed to load with base field is set but harness was not loaded with LoadWithBase, confirming this repo is affected.
• fullsend#5536 (bot-authored PR eligibility): The review→fix auto-handoff failed because the routing logic uses ${ORG_NAME}-review[bot] which doesn't match fullsend-ai-review[bot].
• rhdh-plugins#4025 (boost AGENTS.md improvements): This PR adds evidence that the boost workspace AGENTS.md is missing structural documentation (scripts/ directory not covered).

Proposals filed

• Document scripts/load-secrets.sh and env var sync in boost AGENTS.md (in redhat-developer/rhdh-plugins)